-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added dbt labels as part of columns info when pushing decscriptions #41
base: main
Are you sure you want to change the base?
Conversation
@aibunny Thanks for contributing, appreciate it! As mentioned in #40, I think it needs to be put under Moreover, this should be also added to the opposite way, i.e. from dbt to Superset. Could you please look into that as well? |
Thanks lemme do that. |
Pefect, thanks!
Ignore me, I misread the code changes. |
ok, done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aibunny Thanks again! Leaving a few comments. 😉
Also, would you mind summing up for me what sort of testing you performed?
@@ -63,7 +63,7 @@ def get_datasets_from_superset(superset, superset_db_id): | |||
break | |||
|
|||
assert datasets, "There are no datasets in Superset!" | |||
|
|||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you mind removing the extra whitespaces to keep it aligned with the rest of the code?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please also remove the added whitespace from the rest of your changes?
column_new['description'] = description | ||
|
||
# Check if 'meta' field exists in dbt_columns |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe you could merge this with a previous if
to keep the code DRY? It basically does the same operations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you mind reflecting this one, please?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this better?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you check for expressions when getting column descriptions
Co-authored-by: Michal Koláček <[email protected]>
I ran some functional tests because I didn't have any other tests to work with. Basically, I tested different cases: one with a metafield and labels, another with a metafield but no labels, and finally, a scenario with no metafield at all. |
You mean against dbt and Superset? Which versions did you use? Did it work as expected then? |
yes , I used dbt 1.7 and superset api v1 |
The labels are added in this format which I noticed is commonly used: